Electronic document management system with a content status designation interface

ABSTRACT

The disclosure is directed to system that is configured to manage electronic content and, more specifically, provide a user interface for designating content status with respect to electronic content. The electronic content may be managed by a content collaboration system that manages and stores user-generated content in a series of related pages or documents. Content status may be designated using controls provided via a web-browser user interface and used for tracking and management of electronic content by individual users, which may allow for improved data preservation and more uniform content management.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a nonprovisional patent application of and claimsthe benefit of U.S. Provisional Patent Application No. 63/344,624, filedMay 22, 2022 and titled “Electronic Document Management System with aContent Status Designation Interface,” the disclosure of which is herebyincorporated herein by reference in its entirety.

FIELD

The described embodiments relate generally to an interface for managingelectronic documents and pages. More particularly, the presentembodiments relate to an interface for providing a content status fromwithin the document management interface.

BACKGROUND

Modern enterprises and collaboration platforms typically manage largevolumes of electronic documents and other electronic content created byusers of the platform. A collaboration platform may also allow for liveor dynamic editing of electronic content, which may be viewed by adesignated group of users. In many traditional systems, it can bedifficult to track and manage various versions of the content as itcreated or modified by various users. Additionally, users may hesitateto publish works-in-progress as the newly created content might beeasily confused with completed or static content. As a result, users maycreate and edit content in separate systems, which may not includesatisfactory data backup or data privacy controls, resulting in anoverall content management solution that is non-compliant with datamanagement practices. The systems and techniques described herein may beused to improve the tracking and management of electronic content byindividual users within a single system, which may allow for improveddata preservation and more uniform data privacy controls. The proposedsystem may also provide improved flexibility and utilization for contentcreators and other system users.

SUMMARY

The embodiments and examples described herein are directed to computersystems and computer-implemented methods for operating acomputer-generated interface for editing and viewing electronic content.As described herein, the system may include a backend configured toprovide page content or other electronic content of a contentcollaboration platform over a computer network to a plurality of clientdevices. Each client device may be operating a web browser clientapplication. At the web browser client application and in response to arequest to edit a page at a client device, the system may cause displayof a page-edit user interface within the web browser client application.The page-edit user interface may include page content generated inresponse to user input provided to the client device. The page contentmay be stored by the backend application as a page object. At the webbrowser client application and in response to a hover input over adesignated region, the system may cause display of a content statusoption within the page-edit user interface. The designated region may besubstantially free of page content. In response to a user selection ofthe content status option, the system may cause display of a list ofselectable content status items. In response to a user selection of aparticular selectable content status item of the list of selectablecontent status items, the page object may be modified in accordance withthe user selection of the particular selectable content status item. Inresponse to a request to view the page at the client device of theplurality of client devices, the system may cause display of a page-viewuser interface within the web browser client application. The page-viewuser interface may include a page content region including the pagecontent and a selectable control region including an array of selectablecontrols including a content status control displaying a status indiciacorresponding to the particular selectable content status item.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to representative embodiments illustrated inthe accompanying figures. It should be understood that the followingdescriptions are not intended to limit this disclosure to one includedembodiment. To the contrary, the disclosure provided herein is intendedto cover alternatives, modifications, and equivalents as may be includedwithin the spirit and scope of the described embodiments, and as definedby the appended claims.

FIG. 1 depicts a system for providing content to client devices inaccordance with the embodiments described herein.

FIGS. 2A-2C depict example views of a page-edit interface of a frontendapplication.

FIGS. 3A-3B depict example views of a page-view interface of a frontendapplication.

FIGS. 4A-4C depict example views of an interface of a window element.

FIG. 5 depicts a flow chart corresponding to example operations of aprocess performed using a content collaboration platform or othersimilar system.

FIG. 6 depicts an example hardware for devices of the systems describedherein.

The use of the same or similar reference numerals in different figuresindicates similar, related, or identical items.

Additionally, it should be understood that the proportions anddimensions (either relative or absolute) of the various features andelements (and collections and groupings thereof) and the boundaries,separations, and positional relationships presented therebetween, areprovided in the accompanying figures merely to facilitate anunderstanding of the various embodiments described herein and,accordingly, may not necessarily be presented or illustrated to scale,and are not intended to indicate any preference or requirement for anillustrated embodiment to the exclusion of embodiments described withreference thereto.

DETAILED DESCRIPTION

The systems and techniques described herein are directed to a contentcollaboration platform or other type electronic content managementsystem that allows users to create and publish electronic content usinga client application. In particular, the systems and techniquesdescribed herein may be applicable to content collaboration platformsthat use a web browser client application to generate content creationand editing interfaces for creating electronic content and also contentviewing interfaces for viewing the electronic content. The systems andtechniques described herein are directed to a content status designationinterface that allows each content creator to create and control astatus of a particular page, document, or other electronic content.

In some systems, tracking and management of electronic content may bedifficult due to the fact that electronic content may be in variousstates or stages of completion. Viewing published content, it may bedifficult to determine whether the content is in a final form, is underreview, or is otherwise incomplete or unfinalized. Additionally, asmentioned previously, users may hesitate to publish works-in-progress orearly drafts as the newly created content may be confused with completedor static content. As a result, users may create and edit content inseparate systems, which may not include satisfactory data backup or dataprivacy controls, resulting in an overall content management solutionthat is non-compliant with data management practices. The systems andtechniques described herein may be used to improve the tracking andmanagement of electronic content by individual users within a singlesystem, which may allow for improved data preservation and more uniformdata privacy controls. The proposed system may also provide improvedflexibility and utilization for content creators and other system users.

As described herein, the system may be operated through a clientapplication, which may be a dedicated client application for aweb-enabled application like a web browser. Using the same clientapplication, the user interface may be operated in an edit userinterface (e.g., a page-edit user interface or document-edit userinterface), a view user interface (e.g., a page-view user interface ordocument-view user interface), or another user interface or operationalmode. The client application may allow the user to create, modify, andview a content status depending on the operational mode of the clientapplication. In particular, the client application may provide agraphical interface for allowing the use to classify content using alist of selectable content status items while the page content is beingdisplayed in accordance with an edit user interface or mode. The clientapplication may also provide a content status control having a statusindicia corresponding to a content status while the page content isbeing displayed in accordance with a view interface or mode.

In some embodiments described herein, the controls for allowing thecreation or modification of content status may be hidden until aparticular input is provided to the edit user interface. For example,display of the content status controls may be suppressed or hidden untila hover input or other specified input is provided to the interface. Asdescribed herein, a hover input may include a user direction of cursorelement or other selection control within a particular designated regionwithin the edit user interface. If the cursor element or other selectioncontrol is positioned within the designated region for a thresholdamount of time, the content status controls may be unsuppressed orrevealed. Through the use of the content status controls, the user mayselect from a list of predefined content status items or a user-definedcontent status item. Each item may correspond to a particular state orclassification of the content and may also be associated with apredefined color of a status color palette.

Once associated with the page or document content, the content statusmay be used in conjunction with a content status control within an arrayof selectable controls displayed in accordance with a view interface ormode. The content status control may be selectable in order to causedisplay of page details, status, edit history, and other data obtainedfrom user event logs or interactions with the electronic content. Insome cases, the content status control is selectable to display documentor page metadata, which may include one or more of the aforementioneditems. The content status may also be used to operationalize automationswith respect to system content including bulk actions, scriptedoperations, automated content modifications, or other programmaticoperations performed with respect to content managed by the system. Thecontent status may also be used to establish or discover relationshipsbetween content and may be the subject of electronic content analytics,tracking, or other analysis of content managed by the system.

These foregoing and other embodiments are discussed below with referenceto FIGS. 1, 2A-2C, 3A-3B, 4A-4C, 5, and 6 . However, those skilled inthe art will readily appreciate that the detailed description givenherein with respect to these figures is for explanation only and shouldnot be construed as limiting.

FIG. 1 depicts a simplified diagram of a system, such as describedherein. The system 100 is depicted as implemented in a client-serverarchitecture or client-service architecture, but it may be appreciatedthat this is merely one example and that other communicationsarchitectures are possible. In accordance with the examples provideherein, the system 100 of FIG. 1 can be used to provide a series ofinterfaces to a content collaboration platform or other electroniccontent management system via a computer network. The architecture ofsystem 100 allows for remote access of electronic content using either adedicated client application to access backend servers or a web browserclient application to access one or more web services offered by abackend system. As described herein, the system 100 may be used tocreate, manage, and display content status for electronic content.

The networked computer system or system 100 of FIG. 1 depicts an exampleconfiguration in which multiple client devices 110, 112, 114, and 116may access either host server of a set of host servers 102 via acomputer network 140. The computer network 140 may include a distributednetwork which may include local networks, gateways, and networkingservices provided by one or more internet service providers. The clientdevices 110, 112, 114, and 116 are able to view and share content viathe network 140 either directly or through the various services providedby the set of host servers 102.

The set of host servers 102 may include multiple platform servicesprovided by, for example, first backend 106 and second backend 107. Thefirst backend 106 may for part of a content collaboration platform,which may include a page or document creation and management service,content wiki services, messaging and event feed services, and othercollaboration or data management services. The second backend 107 may asecond instance of similar services or, alternatively, may providedifferent services including, for example, issue tracking services forcreating, managing, and tracking issues for software development, bugtracking, and/or information technology service management (ITSM)services. The second backend 107 may also provide an interface for acode repository, a deployment management system, or other system orservice used to track and manage versioned object storage.

As shown in FIG. 1 , the system 100 includes a set of host servers 102(also referred to as host services) which may be one or more virtual orphysical computing resources (collectively referred in many cases as a“cloud platform”). In some cases, the set of host servers 102 can bephysically collocated or in other cases, each may be positioned in ageographically unique location.

The set of host servers 102 can be communicably coupled to one or moreclient devices by a network 140. Multiple example devices are shown asthe client device 110, 112, 114, and 116. The client devices 110, 112,114, and 116 can be implemented as any suitable electronic device. Inmany embodiments, the client devices 110, 112, 114, and 116 are personalcomputing devices such as desktop computers, laptop computers, or mobilephones. This is merely one example and is not required of allembodiments. An example hardware configuration of a client device isprovided in FIG. 6 , described below.

The set of host servers 102 can be supporting infrastructure for one ormore backend applications, each of which may be associated with aparticular software platform, such as a documentation platform or anissue tracking platform. In particular, a portion of the set of hostservers 102 can be allocated as physical infrastructure supporting afirst platform backend 106 and a different portion of the set of hostservers 102 can be allocated as physical infrastructure supporting asecond platform backend 107. FIG. 6 , described below, provides anexample of various hardware elements that are used by the physicalinfrastructure supporting one or more of the host servers 102.

As noted with respect to other embodiments described herein, the two ormore different platforms may be instantiated over physical resourcesprovided by the set of host servers 102. Once instantiated, the firstplatform backend 106 and the second platform backend 107 cancommunicably couple to a shared data store 130 or other data repository.The data store 130 may include a shared multitenant storage system thathosts data from multiple tenants and multiple platforms for use within aspecific region or realm. In the current example, the data store 130includes content storage 132, which may be used to store user-generatedcontent, content space data, content tree data, content metadata andother electronic content associated with the various backendapplications 106, 107. The user-generated content may be stored as pageobjects, document objects, or other data elements. The data store mayalso include user-profile data stored in user data store 134. The userdata store 134 may include a profile for each registered user of one ormore of the backend systems 106, 107, user permission settings orprofiles, and user history that may include user logs or eventhistories. The data store 130 may also include system store 136, whichmay include system settings, administrator profile settings, contentspace settings, and other system profile data associated with thebackend applications 106, 107.

In the current example, the first platform backend 106 can be configuredto communicably couple to a first platform frontend 122 instantiated bycooperation of a memory and a processor of the client device 110. Onceinstantiated, the first platform frontend 122 can be configured toleverage a display of the client device 110 to render a graphical userinterface so as to present information to a user of the client device110 and so as to collect information from a user of the client device110. As described herein, the first platform frontend 122 may include aweb browser client application that can be used to cause display of anedit user interface or mode (e.g., a page-edit user interface ordocument-edit user interface) a view user interface or mode (e.g., apage-view user interface or document-view user interface), or othercontent creation, management, and viewing interfaces or modes. In somecases, the first platform frontend 122 is a dedicated client applicationthat is able to provide similar functionality with respect to thecontent provided by the host servers 102. Client devices 112, 114, and116 may implement a similar platform frontend, which may be referred toas second, third, or fourth platform frontends.

The first platform frontend 122 can be configured to communicate withthe first backend 106 and/or the second backend 107 over a computernetwork 140, which may include the internet or an established web-basedarchitecture. Information can be transacted by and between the firstplatform frontend 122, the first backend 106, and the second backend 107in any suitable manner or form or format. In many embodiments, as notedabove, the client device 110 and in particular the first platformfrontend 122 can be configured to access either or both of the firstbackend 106 or the second backend 107 via an authentication service 108,which may authenticate a token or other user credentials transmittedalong with a request for access or data provided by the respectivebackends. The authentication service 108 may be configured toauthenticate users in accordance with credentials stored by orregistered with the user data store 134.

FIGS. 2A-2C depict example views of a page-edit user interface or modeof a frontend application. The page-edit user interface 200 allows auser to create and/or edit content of a page or document. As describedherein, the page-edit user interface 200 may be used to generate, edit,or otherwise modify electronic content associated with the user orauthor. The page-edit user interface 200 may also be referred to as acontent-edit user interface, document-edit user interface, edit userinterface, or editor. The page-edit user interface 200 may beimplemented in a web browser client application using HTML, JavaScript,or other web-enabled protocol. The page-edit user interface 200 mayallow the user to create, define, or otherwise modify content statusassociated with user-generated content. The user-generated content maybe referred to herein as page content, document content, electroniccontent, or simply content.

As shown in the sequence of examples depicted in FIGS. 2A-2C, apage-edit user interface 200 may allow a content creator or contentediting user to set or modify a content status associated with the page.The content status can be selected from a subset of predefined contentstatus identifiers that are determined in accordance with anadministrator or page-space profile. A content stats can also beselected from a subset user user-defined content status identifiers thatare determined in accordance with a user profile or which may be createdfrom within the page-edit user interface 200. As described herein, thecontent status allows the user to categorize content prior topublication of after publication in order to help signal the state orstatus of the content to other users. As also described herein,published content may also have access to selectable content statuscontrol, which can be used to cause display of transactional informationrelated to the electronic content, metadata of the electronic content,or other data associated with the electronic content. The content statuscontrol may also include functionality that can be applied to groups ofpages or documents based on the content status including, withoutlimitation, bulk actions, automation scripts, archive and unarchiveactions, search operations, content status changes, and other potentialoperations that may be performed on pages or documents having aparticular content status.

As shown in FIG. 2A, the content status options or controls, which maybe displayed in designated region 250 may be suppressed or hidden duringa normal editing or viewing mode of the page-edit user interface.However, in response to a hover command (e.g., a directing a cursorwithin the designated region 250 for a predefined or threshold period oftime), a content status option or content status controls 210 may beunsuppressed or displayed, as shown in FIGS. 2B and 2C. As a result, thedisplay of the controls for creating or modifying content status mayremain hidden from view until they are needed by the user. While a hovercommand is used in this example, there may be other user inputs thatcause the display of the content status options or controls 210.Alternatively, in some cases, the display of the content status optionof content status controls 210 is not suppressed or hidden, and thus,appears during normal editing operations of the page or document.

FIG. 2A depicts a page-edit user interface 200 having an example set ofcontrols and user interface elements that facilitate the creation andmodification of user-generated content. Specifically, as shown in FIG.2A, the page-edit user interface 200 may include page content 202 in apage content region, a toolbar panel 204, a publication control 206,and/or a publication status of the page corresponding to a page beingdisplayed on the page-edit user interface 200, and a user profile icon208 of a user. The various controls and layout of the page-edit userinterface 200 may be determined or controlled by one or more settingsassociated with the content space or a content space administrator.

As shown in FIG. 2A, the page-edit user interface 200 may include avariety of other elements and controls. As shown in FIG. 2A, the pagecontent 202 may include and display information, including but notlimited to, a title of the page or document. In some embodiments, thetitle of the page may be displayed as a first line below the designatedregion 250, which may contain suppressed display of one or more controlsor user-interface elements. One or more users or members who contributedto development of the page, and one or more sections providing detailsor page content 202 may be displayed in the page content region. Thepage content 202 may include multimedia content, embedded content,linked content, and other electronic content associated with the page ordocument.

By way of a non-limiting example, the page content 202 may also includea table of content (ToC), a summary or outline of the page, and so on.In some embodiments, the ToC, and/or the summary or outline of the pagemay be manually or automatically generated. The ToC, and/or the summaryor outline of the page may be generated using a user-provided script orinstructions. For example, the ToC may be automatically generated basedon a heading style, such as a font size, an indentation, and so on. Insome cases, the summary or outline may be generated automatically basedon parsing of the content of each section of a page and/or the pagecontent 202.

In some embodiments, the toolbar panel 204 may include and display anarray of selectable controls or various menu options associated withmanagement of the page according to the page-edit user interface. Thetoolbar panel 204 may include a set of selectable controls or optionsthat can be used for creating or modifying user-generated content intothe editable region 201 or editor of the page-edit user interface 200.By way of a non-limiting example, the array of selectable controls orvarious menu options in the toolbar panel 204 may include a selectablecontrol or a menu option for formatting the page (e.g., a font type, afont size, line spacing, indentation, inserting external content as alink or a reference), and so on.

In some embodiments, and by way of a non-limiting example, the user, whois shown by the user profile icon 208, may select a specific publicationstatus of the page. For example, the user may select a publicationcontrol 206 shown in the page-edit user interface 200 to set or modify apublication state of the page. For example, the publication control 206may be used to publish, unpublish, or otherwise control the availabilityof the content for viewing by other users. In the published state of thepage, the page content may be available to a predefined set of users ofa content collaboration platform according to access rights managementsettings for the page and/or a user profile associated with one or moreother users. In some cases, the publication status may be limited to adefined set of users having accounts with the content collaborationsystem and may be referred to as an internal or limited publication. Inother cases, the publication status may allow all users (the entirepublic) to view the content via an externally available address like auniform resource locator (URL) or other hierarchical path.

In some embodiments, and by way of a non-limiting example, the pagecontent, the status indicator corresponding to the page, the accessrights management settings corresponding to the page, and so on, may bestored as a data field or metadata of a page object or document objectin a database that is communicatively coupled with the contentcollaboration platform. The page or document object may include theuser-generated content (e.g., content 202), page or document metadata,and/or elements of a transaction history or event log. In some cases,the page object or document object is stored as multiple data entriesthat may be stored in a distributed fashion but are able to be accessedusing a common page or document identifier (e.g., page ID or documentID).

FIG. 2B depicts another example view of the page-edit user interface 200of the frontend application. As discussed previously, the page-edit userinterface 200 as shown in FIG. 2B includes a designated region 250 inwhich one or more content status options may be displayed as graphicaluser interface (GUI) elements. In some cases, the designated region 250may be positioned above a first line of the page content. Accordingly,the designated region 250 may be substantially or completely free fromthe page content. In some cases, the designated region 250 may bepositioned at other locations on the page. Other controls or GUIelements may also be displayed within the designated region includingbut not limited to, “add emoji,” “add header image,” “add page contentcontributors,” and so on. Similarly, these controls may be revealed orunsuppressed in response to a particular user input (e.g., a covercommand).

As mentioned previously, when a user hovers or cause a dwell of a pagecontrol pointer 203 (e.g., a cursor) at or within a specific area (e.g.,the designated region 250) of the page-edit user interface 200. Thisaction or input may be referred to internally as a hover command orhover input and may be used to reveal a content status option as part ofa set of revealable controls which may include additional options orvalues may be displayed to the user. In some cases, the additionaloptions or values may be displayed to the user as a radio button, acheck box, or a free form of user input (e.g., the user may create herown value). In response to the user positioning the cursor away from theGUI element, the display of the additional options or values may besuppressed.

In the example of FIG. 2C, in response to a user selecting the GUIelement associated with the “add page status” content status option 210,a window element 220 may be displayed which includes additional optionsand controls. The window element 220 may be a pop-up or floating windowelement that overlays or overlaps at least a portion of the page content202 being displayed. In some embodiments, the interface provided by thewindow element 220 includes a list of selectable content status items224, a text entry region 222, and other controls or selections. As shownin FIG. 2C, the list of selectable content status items 224 may includeentries for “rough draft,” “in progress,” and “ready for review.” Insome embodiments, the number of selectable content status items 224 thatare displayed may be predetermined or configurable. The selectable items224 may be determined in accordance with an administrator profile orother system-level setting. These settings may be specific for aparticular space, domain, or set of pages or documents. In someembodiments, the default values may be selected based on one or morefactors, including but not limited to, current stage of the pagedevelopment, history of previous page statuses of the page, history ofprevious page statuses set by the user, a set of default page statusvalues corresponding to a space or a domain in which the page iscreated. In this case, the space or the domain may be associated with aparticular project and/or a group of users. In some cases, and by way ofa non-limiting example, each selectable content status item 224 may bedisplayed using a different font and/or a different color in accordancewith a predefined color palette.

In some embodiments, the selectable content status items 224 may alsoinclude a list of user-created content status item. Creation of customcontent status items is described below with respect to FIGS. 4A-4C. Asshown in FIG. 2C, a custom content status item may be created inresponse to user text input provided to the text entry region 222. Forexample, the user may set the custom page status as “Draft for Deliveryon May 18, 2022,” or “Draft for John,” or other user-defined status.

In accordance with the user selection of a particular selectable contentstatus item, the page object or document object associated with thedisplayed page or document content 202 may be modified. In some cases,the content status may be stored in the metadata of the page ordocument. In some cases, the content status is also reflected in adocument index or other registry to facilitate searching and retrievalof content associated with a common or designated content status.

In some embodiments, the user-created custom page statuses may beavailable to the user for other pages that the user is working on in thesame and/or other domain or space. Accordingly, the user-created custompage statuses may be available to the user for selection using the listof user-defined content status items. In some cases, the number ofuser-created custom page statuses displayed for selection using the pulldown list may be limited to predetermined or preconfigured number ofcustom page statuses, for example, 5 or fewer custom page statues.

FIGS. 3A-3B depict example views of a page-view user interface 300 of afrontend application. The page-view user interface 300 allows authorizedusers to view content of a page. The page-view user interface 300 mayallow for the viewing of content that has been published, either to alimited set of users, or to the public, who are able to access thecontent at a particular endpoint or URL. The page-view user interface300 may also be referred to herein as a content-view user interface,document-view user interface, view user interface, or viewer. Thepage-view user interface 300 may be implemented in a web browser clientapplication using HTML, JavaScript, or other web-enabled protocol. Thepage-view user interface 300 may allow a designated user to view,browse, search, or otherwise consume the page content 302. In manycases, the page-view user interface 300 allows for the creation ofadditional content, which may be in the form of embedded comments,user-generated tags, or other similar content. However, modification oredit of the underlying page content 302 may be restricted or prohibitedfrom within the page-view user interface 300.

As shown in FIG. 3A, the page-view user interface 300 may includeadditional elements that facilitate navigation and consumption ofelectronic content. For example, the page-view user interface 300includes a page tree 306, which may be displayed on the left panel ofthe page. The page tree 306 (also referred to as a hierarchicalnavigation panel, navigational document tree, or content tree) mayinclude one or more tree elements or selectable items, each itemselectable and configured to cause display of a respective page ordocument in the main panel in response to a user selection. In oneexample, in response to the user's selection of a tree entry 304, thepage-view user interface 300 may automatically navigate the user to apage or document associated with the selected entry, which may be causedto be displayed in the main or page content region of the page-view userinterface. In some embodiments, and by way of a non-limiting example,the page content region may be on the right and/or center panel of thepage.

Further, the page-view user interface 300 may also include and displayan array of selectable controls 304. The array of selectable controls304 may include, but not limited to, a content status control 310. Thecontent status control 310 may display a status indicia corresponding tothe content of a section of the page that is displayed in the pagecontent region. Accordingly, when the user accesses another tree entry,then the status indicia in the content status control 310 may be updatedfor displaying on the display. As shown in in FIGS. 3A-3B, the contentstatus control 310 may include current page status along with a userselected color code and/or symbol for the particular page status value.The content status control 310 may be set by the author of the page ordocument but may otherwise be restricted for modification by otherusers. In some cases, an administrator or space admin may override orhave the ability to change the permissions associated with a change inthe content control status 310.

The content status control 310 serves as both a notification of thestatus of the page or document while also providing a control to viewadditional data or take additional actions with respect to the page ordocument. As discussed earlier, the content status control 310 allows anauthor or content creator to signal a state or status of the draft,independent of publication state. Accordingly, while content may bepublished and available for viewing by a designated group of users, theusers are put on notice regarding whether the draft is likely to changeover time or is in a final or near-final form. The content status mayalso indicate a user or user group that is responsible for reviewing orapproving the content, which may facilitate user feedback or documentapproval actions.

In some cases, the content status may be advanced in accordance with aworkflow or a programmable sequence that is able to automatically changein accordance with a time threshold, a user approval action, a taskcompletion, or other system event. For example, content that isdesignated as a “rough draft” may automatically advance to “final draft”or “unmodified draft” after a designated amount of time has elapsedwithout additional edits or modifications and/or approval from a user isreceived. The programed workflow or state transition of the contentstatus may also be driven by one or more system events or automationsequences. For example, the content status for a group or set of contentitems may be advanced in accordance with a bulk action command orautomation script configured to modify page content or document contentin a designated page space or other domain.

In some cases, the content status may be used to automatically triggerone or more messages or communications in accordance with a timingcriteria or other predetermined rule or criteria. For example, contentthat is designated as having an early or rough draft content status andalso not modified for an amount of time exceeding a predeterminedthreshold may cause the system to generate a notification or a messageto the user including a prompt to either modify the status or edit thecontent. In some cases, the message may be transmitted to other usersassociated with the author including a page administrator, supervisor,or content manager for the system. In some cases, the transmittedmessages include embedded links or selectable elements that mayautomatically advance or modify the content status in response to a userinput directly in the body of the message.

As shown in FIG. 3B, in response to the content status control 310 beingselected, additional data or information or options may be caused to bedisplayed. In this example, an overlay window may be displayed withadditional information regarding the content and one or more options toview additional information or take additional actions. Specifically,the window 312 overlays or overlaps a portion of the content 302 andincludes page status details, such as the last date and timecorresponding to the page status update may be displayed. In some cases,a history of page status changes may also be displayed. In some cases,the user may provide a date range, a page status set or changed by aspecific user, and/or a particular page status value as one or morefilter options to view the history of page status changes. Additionaldetails including data extracted from the page or document metadata mayalso be displayed in the window 312. In some cases, information from atransaction history or user event logs may be obtained and a summary ofwhich may be displayed in the window 312.

In some implementations, the window 312 may also include one or moreactions that can be performed with respect to the content or all contentwithin a space or domain having a similar or the same content status.For example, the window 312 may include an option that can be used toinvoke or specify a set of actions for all content items (documents orpages) having the designated status. Example actions include an actionto change the content status, an action to retrieve all content havingthe designated content status, an action to archive all content havingthe designated content status, or any other system action that can beperformed on a group of items in accordance with a script or automationsequence.

FIGS. 4A-4C depict example views of an interface of a window element.Specifically, FIGS. 4A-4C depict an example sequence of operations forgenerating a custom or user defined page status designator. For example,view 400 a, shown in FIG. 4A, may correspond with a GUI element (or awindow element) associated with the “add page status” content statusoption (e.g., item 210 of FIGS. 2B and 2C). When a user selects orhovers over page control pointer at or within the specific area of theGUI element associated with the “add page status” content status option,a pop-up or floating window element overlaying over the page displayingcontent of the page may be generated. As shown in the view 400 a, theuser may select a custom page status by providing user input into a textbox. For example, the user may select the custom page status to be“Internal Only!” as the page should not be available to people outsidean organization and/or a group. In some embodiments, and by way of anon-limiting example, the custom page status value may be limited to aparticular word or character count length limit. For example, the custompage status may be limited to 20 characters or 5 words.

In some embodiments, the most recent or current custom page status valuemay be displayed on the top as a label of a pull down list including allor predetermined number of custom page status values used by a user forthe same page being edited or created, and/or other pages created and/oredited by the user in the same or different space or domain.

In some embodiments, the user may select a particular custom page statusvalue and may also delete it. In some cases, the custom page statusvalues that are created by the user and not currently being applied toany page may be automatically deleted upon periodic or aperiodicevaluation of the user-created custom page status values and whetherthey are being applied to any page.

In some embodiments, as shown in a view 400 b in FIG. 4B, the user mayselect a particular color to associate with a custom page status value.The color may be selected in accordance with a predefined color palette.By way of a non-limiting example, the user may also select a specificfont type and/or a specific font size to associate with the custom pagestatus value.

In some embodiments, as shown in a view 400 c in FIG. 4C, the newlycreated status is added to the list of selectable items used to assign acontent status to a page or other electronic content. The newly createdcontent status may be stored or associated with a user profile or otheruser-related setting stored on the system. In some cases, a certainnumber of user-created custom page status values may be displayed undera label, such as “custom.” The most recent or current custom page statusvalue may be displayed on the top. However, in some cases, the user mayalso display the custom page status values in any other order, such asalphabetically ascending or alphabetically descending, and so on.

In some cases, the one or more custom page status values may besuggested to the user based on a user profile, a group profile, anadministrator profile, a space and/or a domain in which the page may becreated and/or edited, a current stage of the page development, and soon. For example, the one or more custom page status values suggested tothe user may be “Rough Draft,” “In progress,” and/or “Ready for Review,”and or other items.

Accordingly, in accordance with some embodiments, as shown in FIGS.4A-4C, user-defined selectable content item, such as a custom pagestatus value may be generated. Further, the user profile may be updatedto display the user-created custom page status values for the user toselect. In some cases, the user-created custom page status values may beavailable across domains and/or spaces. In some cases, the user-createdcustom page status values may be available only to the page and/or thedomain/space in which the page is created.

FIG. 5 depicts a flow chart corresponding to example operations of aprocess performed using a content collaboration platform or othersimilar system, in accordance with some embodiments. As shown in a flowchart 500 in FIG. 5 , at 502, in response to receiving, at a hostserver, such as a first platform backend 106 or a second platformbackend 107, and from a client device, such as the client device 110,112, 114, or 116, a request to edit a page at the client device, thehost server may cause display of a page-edit user interface on theclient device. The page may be maintained by the content collaborationplatform, as described herein, in accordance with some embodiments. Thecontent collaboration platform, thus, may host electronic documents,such as web pages, files, audio and/or video content, and so on, andallow users of the content collaboration platform to create, edit,modify, and/or delete the electronic documents, for example, a page (ora web page), being managed by the content collaboration platform.

In some embodiments, an example view of the page-edit user interfacedisplayed on the client device may be as shown in FIGS. 2A-2C. As shownin FIGS. 2A-2C, the page-edit user interface may be generated anddisplayed as a web browser application instance. The page-edit userinterface thus may be generated according to hypertext transfer protocol(HTTP) or hypertext transfer protocol secure (HTTPS) protocol usinghypertext markup language (HTML), JavaScript Object Notation (JSON),and/or a custom document format to transfer data between the clientdevice and the host server of the content collaboration platform.

At 504, a user may generate and/or edit page content of the displayedwebpage. For example, the user may add a new page content or edit pagecontent using an array of selectable controls or various menu optionsassociated with management of the page. The array of selectable controlsor various menu options may be displayed in the toolbar panel 204. Theuser-generated or user-edited page content may be stored as a pageobject by the content collaboration platform, at 506. In some cases, thepage object may be stored in a database as a database object havingvarious fields or attributes corresponding to the page object. In oneexample, various fields or attributes corresponding to the page objectmay include, but not limited to, page content, a user who created thedocument, a user who last edited the document, history of changes of thepage content, date and time corresponding to each change of the pagecontent, and so on.

At 508, in response to the user hovering a cursor in a designatedregion, such as the designated region 250 b, a content status option maybe displayed on the generated page-edit user interface. The displayedcontent status option may be suppressed when the user moves the cursoraway from the designated region. The content status option, as describedherein, may provide information about status of the page to a user ofthe content collaboration platform. The status of the page may be set bya creator or editor of the page.

At 510, a list of selectable content status items may be displayed tothe user. The list of selectable content status items may includedefault and/or suggested page status values. In some cases, the list ofselectable content status items may also include one or moreuser-created or custom page status options. The user-created or custompage status options displayed in the list of selectable content statusitems may be limited to a predetermined number of page status options,for example, the last five page status options. In some cases, theuser-created or custom page status options displayed in the list ofselectable content status items may be user-created or custom pagestatuses that the user has created for any page and not just the pagebeing created and/or edited by the user. In some cases, the user-createdor custom page status options displayed in the list of selectablecontent status items may be page specific, and, therefore, includeuser-created or custom page status options created or set by any user ofthe content collaboration platform for the page. In some cases, theuser-created or custom page status options displayed in the list ofselectable content status items may be domain or space specific, asdescribed herein, in accordance with some embodiments. In some cases,the user may create a new page status as described here in withreference to FIGS. 4A-4C.

At 512, in response to the user's selection of page status from the pagestatus options displayed in the list of selectable content status items,the page object may be modified, and updated by the contentcollaboration platform. At 514, in response to receiving, at the contentcollaboration platform, and from a client device of any user of thecontent collaboration platform, a request to view the page being managedby content collaboration platform, a page-view user interface may bedisplayed on the client device. In some embodiments, an example view ofthe page-view user interface displayed on the client device may be asshown in FIGS. 3A-3B. As shown in FIGS. 3A-3B, the page-view userinterface may be generated and displayed as a web browser applicationinstance. The page-view user interface thus may be generated accordingto hypertext transfer protocol (HTTP) or hypertext transfer protocolsecure (HTTPS) protocol using hypertext markup language (HTML),JavaScript Object Notation (JSON), and/or a custom document format totransfer data between the client device and the host server of thecontent collaboration platform.

At 516, the page-view user interface displayed on the client device maydisplay page content and selectable control region in page contentregion of the page-view user interface. In some embodiments, and by wayof a non-limiting example, the page content region may be on the rightand/or center panel of the page. Further, as illustrated in thepage-view user interface 300 displayed on the client device may alsoinclude and display an array of selectable controls 308. The array ofselectable controls 308 may include, but not limited to, a contentstatus control 310. The content status control 310 may display a statusindicia corresponding to the content of a section of the page that isdisplayed in the page content region.

In some embodiments, as shown in the page-view user interface 300, thecontent status control 310 of the page-view user interface may includecurrent page status along with a user selected color code for theparticular page status value. By way of a non-limiting example,additionally or alternatively, additional page status details, such asthe last date and time corresponding to the page status update may bedisplayed. In some cases, a history of page status changes may also bedisplayed. In some cases, the user may provide a date range, a pagestatus set or changed by a specific user, and/or a particular pagestatus value as one or more filter options to view the history of pagestatus changes.

FIG. 6 shows a sample electrical block diagram of an electronic device600 that may perform the operations described herein. The electronicdevice 600 may in some cases take the form of any of the electronicdevices described with reference to FIGS. 1-4C, including clientdevices, and/or servers or other computing devices associated with thecollaboration system 100. The electronic device 600 can include one ormore of a processing unit 602, a memory 604 or storage device, inputdevices 606, a display 608, output devices 610, and a power source 612.In some cases, various implementations of the electronic device 600 maylack some or all of these components and/or include additional oralternative components.

The processing unit 602 can control some or all of the operations of theelectronic device 600. The processing unit 602 can communicate, eitherdirectly or indirectly, with some or all of the components of theelectronic device 600. For example, a system bus or other communicationmechanism 614 can provide communication between the processing unit 602,the power source 612, the memory 604, the input device(s) 606, and theoutput device(s) 610.

The processing unit 602 can be implemented as any electronic devicecapable of processing, receiving, or transmitting data or instructions.For example, the processing unit 602 can be a microprocessor, a centralprocessing unit (CPU), an application-specific integrated circuit(ASIC), a digital signal processor (DSP), or combinations of suchdevices. As described herein, the term “processing unit” is meant toencompass a single processor or processing unit, multiple processors,multiple processing units, or other suitably configured computingelement or elements.

It should be noted that the components of the electronic device 600 canbe controlled by multiple processing units. For example, selectcomponents of the electronic device 600 (e.g., an input device 606) maybe controlled by a first processing unit and other components of theelectronic device 600 (e.g., the display 608) may be controlled by asecond processing unit, where the first and second processing units mayor may not be in communication with each other.

The power source 612 can be implemented with any device capable ofproviding energy to the electronic device 600. For example, the powersource 612 may be one or more batteries or rechargeable batteries.Additionally, or alternatively, the power source 612 can be a powerconnector or power cord that connects the electronic device 600 toanother power source, such as a wall outlet.

The memory 604 can store electronic data that can be used by theelectronic device 600. For example, the memory 604 can store electronicdata or content such as, for example, audio and video files, documentsand applications, device settings and user preferences, timing signals,control signals, and data structures or databases. The memory 604 can beconfigured as any type of memory. By way of example only, the memory 604can be implemented as random access memory, read-only memory, Flashmemory, removable memory, other types of storage elements, orcombinations of such devices.

In various embodiments, the display 608 provides a graphical output, forexample associated with an operating system, user interface, and/orapplications of the electronic device 600 (e.g., a chat user interface,an issue-tracking user interface, an issue-discovery user interface,etc.). In one embodiment, the display 608 includes one or more sensorsand is configured as a touch-sensitive (e.g., single-touch, multi-touch)and/or force-sensitive display to receive inputs from a user. Forexample, the display 608 may be integrated with a touch sensor (e.g., acapacitive touch sensor) and/or a force sensor to provide a touch-and/or force-sensitive display. The display 608 is operably coupled tothe processing unit 602 of the electronic device 600.

The display 608 can be implemented with any suitable technology,including, but not limited to, liquid crystal display (LCD) technology,light emitting diode (LED) technology, organic light-emitting display(OLED) technology, organic electroluminescence (OEL) technology, oranother type of display technology. In some cases, the display 608 ispositioned beneath and viewable through a cover that forms at least aportion of an enclosure of the electronic device 600.

In various embodiments, the input devices 606 may include any suitablecomponents for detecting inputs. Examples of input devices 606 includelight sensors, temperature sensors, audio sensors (e.g., microphones),optical or visual sensors (e.g., cameras, visible light sensors, orinvisible light sensors), proximity sensors, touch sensors, forcesensors, mechanical devices (e.g., crowns, switches, buttons, or keys),vibration sensors, orientation sensors, motion sensors (e.g.,accelerometers or velocity sensors), location sensors (e.g., globalpositioning system (GPS) devices), thermal sensors, communicationdevices (e.g., wired or wireless communication devices), resistivesensors, magnetic sensors, electroactive polymers (EAPs), strain gauges,electrodes, and so on, or some combination thereof. Each input device606 may be configured to detect one or more particular types of inputand provide a signal (e.g., an input signal) corresponding to thedetected input. The signal may be provided, for example, to theprocessing unit 602.

As discussed above, in some cases, the input device(s) 606 include atouch sensor (e.g., a capacitive touch sensor) integrated with thedisplay 608 to provide a touch-sensitive display. Similarly, in somecases, the input device(s) 606 include a force sensor (e.g., acapacitive force sensor) integrated with the display 608 to provide aforce-sensitive display.

The output devices 610 may include any suitable components for providingoutputs. Examples of output devices 610 include light emitters, audiooutput devices (e.g., speakers), visual output devices (e.g., lights ordisplays), tactile output devices (e.g., haptic output devices),communication devices (e.g., wired or wireless communication devices),and so on, or some combination thereof. Each output device 610 may beconfigured to receive one or more signals (e.g., an output signalprovided by the processing unit 602) and provide an output correspondingto the signal.

In some cases, input devices 606 and output devices 610 are implementedtogether as a single device. For example, an input/output device or portcan transmit electronic signals via a communications network, such as awireless and/or wired network connection. Examples of wireless and wirednetwork connections include, but are not limited to, cellular, Wi-Fi,Bluetooth, IR, and Ethernet connections.

The processing unit 602 may be operably coupled to the input devices 606and the output devices 610. The processing unit 602 may be adapted toexchange signals with the input devices 606 and the output devices 610.For example, the processing unit 602 may receive an input signal from aninput device 606 that corresponds to an input detected by the inputdevice 606. The processing unit 602 may interpret the received inputsignal to determine whether to provide and/or change one or more outputsin response to the input signal. The processing unit 602 may then sendan output signal to one or more of the output devices 610, to provideand/or change outputs as appropriate.

As used herein, the phrase “at least one of” preceding a series ofitems, with the term “and” or “or” to separate any of the items,modifies the list as a whole, rather than each member of the list. Thephrase “at least one of” does not require selection of at least one ofeach item listed; rather, the phrase allows a meaning that includes at aminimum one of any of the items, and/or at a minimum one of anycombination of the items, and/or at a minimum one of each of the items.By way of example, the phrases “at least one of A, B, and C” or “atleast one of A, B, or C” each refer to only A, only B, or only C; anycombination of A, B, and C; and/or one or more of each of A, B, and C.Similarly, it may be appreciated that an order of elements presented fora conjunctive or disjunctive list provided herein should not beconstrued as limiting the disclosure to only that order provided.

One may appreciate that although many embodiments are disclosed above,that the operations and steps presented with respect to methods andtechniques described herein are meant as exemplary and accordingly arenot exhaustive. One may further appreciate that alternate step order orfewer or additional operations may be required or desired for particularembodiments.

Although the disclosure above is described in terms of various exemplaryembodiments and implementations, it should be understood that thevarious features, aspects, and functionality described in one or more ofthe individual embodiments are not limited in their applicability to theparticular embodiment with which they are described, but instead can beapplied, alone or in various combinations, to one or more of the someembodiments of the invention, whether or not such embodiments aredescribed, and whether or not such features are presented as being apart of a described embodiment. Thus, the breadth and scope of thepresent invention should not be limited by any of the above-describedexemplary embodiments but is instead defined by the claims hereinpresented.

Furthermore, the foregoing examples and description of instances ofpurpose-configured software, whether accessible via API as arequest-response service, an event-driven service, or whether configuredas a self-contained data processing service are understood as notexhaustive. In other words, a person of skill in the art may appreciatethat the various functions and operations of a system such as describedherein can be implemented in a number of suitable ways, developedleveraging any number of suitable libraries, frameworks, first orthird-party APIs, local or remote databases (whether relational, NoSQL,or other architectures, or a combination thereof), programminglanguages, software design techniques (e.g., procedural, asynchronous,event-driven, and so on or any combination thereof), and so on. Thevarious functions described herein can be implemented in the same manner(as one example, leveraging a common language and/or design), or indifferent ways. In many embodiments, functions of a system describedherein are implemented as discrete microservices, which may becontainerized or executed/instantiated leveraging a discrete virtualmachine, that are only responsive to authenticated API requests fromother microservices of the same system. Similarly, each microservice maybe configured to provide data output and receive data input across anencrypted data channel. In some cases, each microservice may beconfigured to store its own data in a dedicated encrypted database; inothers, microservices can store encrypted data in a common database;whether such data is stored in tables shared by multiple microservicesor whether microservices may leverage independent and separatetables/schemas can vary from embodiment to embodiment. As a result ofthese described and other equivalent architectures, it may beappreciated that a system such as described herein can be implemented ina number of suitable ways. For simplicity of description, manyembodiments that follow are described in reference to an implementationin which discrete functions of the system are implemented as discretemicroservices. It is appreciated that this is merely one possibleimplementation.

In addition, it is understood that organizations and/or entitiesresponsible for the access, aggregation, validation, analysis,disclosure, transfer, storage, or other use of private data such asdescribed herein will preferably comply with published andindustry-established privacy, data, and network security policies andpractices. For example, it is understood that data and/or informationobtained from remote or local data sources, only on informed consent ofthe subject of that data and/or information, should be accessedaggregated only for legitimate, agreed-upon, and reasonable uses.

What is claimed is:
 1. A computer-implemented method for operating acomputer-generated interface for editing and viewing electronic documentcontent, the method comprising: at a backend configured to provide pagecontent of a content collaboration platform over a computer network to aplurality of client devices, each client device operating a web browserclient application: in response to a request to edit a page at a clientdevice of the plurality of client devices: cause display of a page-edituser interface within the web browser client application, the page-edituser interface including page content generated in response to userinput provided to the client device; cause the page content to be storedby the backend as a page object; and in response to a hover input over adesignated region, cause display of a content status option within thepage-edit user interface, the designated region substantially free ofpage content; in response to a user selection of the content statusoption, cause display of a list of selectable content item statuses in awindow element that overlays at least a portion of the page content, thewindow element comprising a text entry region configured to receiveuser-entered text; in response to receiving user-entered text in thetext entry region, generate a new user-defined selectable content itemstatus; update a user-specific profile to include a new user-definedcontent status option that corresponds to the new user-definedselectable content item status; and in response to a user selection of aparticular selectable content item status of the list of selectablecontent item statuses including the new user-defined content statusoption, modify the page object in accordance with the user selection ofthe particular selectable content item status; in response to a requestto view the page at the client device of the plurality of clientdevices, cause display of a page-view user interface within the webbrowser client application, the page-view user interface including apage content region including the page content and a selectable controlregion including an array of selectable controls including a contentstatus control displaying a status indicia corresponding to theparticular selectable content item status.
 2. The computer-implementedmethod of claim 1, wherein: the list of selectable content item statusescomprises: a first set of selectable content item statuses determined inaccordance with an administrator profile; and a second set of selectablecontent item statuses determined in accordance with the user-specificprofile.
 3. The computer-implemented method of claim 1, wherein: thewindow element comprises a color designation input; in response to auser selection of the color designation input, provide a selectablecolor palette; and in response to a user selection of a particular colorof the selectable color palette, assign the particular color to the newcontent status option.
 4. The computer-implemented method of claim 3,wherein in accordance with a user selection of the new user-definedselectable content item status, the page-view user interface displaysthe content status control with an element having the particular color.5. The computer-implemented method of claim 1, wherein: the contentstatus control is selectable when the page is displayed in the page-viewuser interface; and in response to a user selection of the contentstatus control, a content status window is displayed, the content statuswindow at least partially overlapping the page content, the contentstatus window comprising a time indicating a last content status change.6. The computer-implemented method of claim 1, wherein: the designatedregion of the page-edit user interface is positioned above a first lineof the page content; the hover input comprises positioning a cursor overthe designated region; and in response to positioning the cursor awayfrom the designated region, display of the content status option issuppressed.
 7. A system for operating a computer-generated interface forediting and viewing electronic document content, the system comprising:memory storing a backend application configured to provide page contentof a content collaboration platform over a computer network to aplurality of client devices, each client device operating a web browserclient application; and one or more processors operably coupled to thememory and when executing the backend application, cause the system to:in response to a request to edit a page at a client device of theplurality of client devices: cause display of a page-edit user interfacewithin the web browser client application, the page-edit user interfaceincluding page content generated in response to user input provided tothe client device; cause the page content to be stored by the backendapplication as a page object; and in response to a hover input over adesignated region, cause display of a content status option within thepage-edit user interface, the designated region substantially free ofpage content; in response to a user selection of the content statusoption, cause display of a list of selectable content item statuses in awindow element that overlays at least a portion of the page content, thewindow element comprising a text entry region configured to receiveuser-entered text; in response to receiving user-entered text in thetext entry region, generate a new user-defined selectable content itemstatus; update a user-specific profile to include a new user-definedcontent status option that corresponds to the new user-definedselectable content item status; and in response to a user selection of aparticular selectable content item status of the list of selectablecontent item statuses including the new user-defined content statusoption, modify the page object in accordance with the user selection ofthe particular selectable content item status; in response to a requestto view the page at the client device of the plurality of clientdevices, cause display of a page-view user interface within the webbrowser client application, the page-view user interface including apage content region including the page content and a selectable controlregion including an array of selectable controls including a contentstatus control displaying a status indicia corresponding to theparticular selectable content item status.
 8. The system of claim 7,wherein: the list of selectable content item statuses comprises: a firstset of selectable content item statuses determined in accordance with anadministrator profile; and a second set of selectable content itemstatuses determined in accordance with the user-specific profile.
 9. Thesystem of claim 7, wherein: the window element comprises a colordesignation input; in response to a user selection of the colordesignation input, provide a selectable color palette; and in responseto a user selection of a particular color of the selectable colorpalette, assign the particular color to the new content status option.10. The system of claim 9, wherein in accordance with a user selectionof the new user-defined selectable content item status, the page-viewuser interface displays the content status control with an elementhaving the particular color.
 11. The system of claim 7, wherein: thecontent status control is selectable when the page is displayed in thepage-view user interface; and in response to a user selection of thecontent status control, a content status window is displayed, thecontent status window at least partially overlapping the page content,the content status window comprising a time indicating a last contentstatus change.
 12. The system of claim 7, wherein: the designated regionof the page-edit user interface is positioned above a first line of thepage content; the hover input comprises positioning a cursor over thedesignated region; and in response to positioning the cursor away fromthe designated region; suppress display of the content status option.13. A computer-implemented method comprising: at a backend configured toprovide electronic content over a computer network to a plurality ofclient devices, each client device operating a web browser clientapplication: in response to a request to edit a document at a clientdevice of the plurality of client devices: cause display of adocument-edit user interface within the web browser client application,the document-edit user interface including electronic content generatedin response to a first user input provided to the client device; causethe electronic content to be stored by the backend as a document object;and in response to a second user input at a designated region, causedisplay of a list of selectable content item statuses in a windowelement that overlays at least a portion of the electronic content, thewindow element comprising a text entry region configured to receiveuser-entered text; in response to receiving user-entered text in thetext entry region, generate a new user-defined selectable content itemstatus; and update a user-specific profile to include a new user-definedcontent status option that corresponds to the new user-definedselectable content item status; and in response to a user selection of aparticular selectable content item status of the list of selectablecontent item statuses including the new user-defined content statusoption, modify the document object in accordance with the user selectionof the particular selectable content item status; in response to arequest to view the document at the client device of the plurality ofclient devices, cause display of a document-view user interface withinthe web browser client application, the document-view user interfaceincluding a content region including the electronic content and aselectable control region including an array of selectable controlsincluding a content status control displaying a status indiciacorresponding to the particular selectable content item status.
 14. Thecomputer-implemented method of claim 13, wherein: the list of selectablecontent item statuses is displayed in response to a user selection of acontent status option; and the content status option is displayed inresponse to a hover input over the designated region.
 15. Thecomputer-implemented method of claim 14, wherein: the designated regionof the document-edit user interface is positioned above a first line ofthe electronic content; the hover input comprises positioning a cursorover the designated region; and in response to positioning the cursoraway from the designated region, display of the content status option issuppressed.
 16. The computer-implemented method of claim 13, wherein:the list of selectable content statuses comprises: a first set ofselectable content item statuses determined in accordance withadministrator profile; and a second set of selectable content itemstatuses determined in accordance with the user-specific profile. 17.The computer-implemented method of claim 13, wherein: the content statuscontrol is selectable when the document is displayed in thedocument-view user interface; and in response to a user selection of thecontent status control, a content status window is displayed, thecontent status window at least partially overlapping the electroniccontent, the content status window displaying document metadata.